Skip to content
Skills Library
Security · Review & audit

batch-request-object-isolation

/batch-request-object-isolation

Check that batched requests cannot mix identities, credentials or objects so one operation borrows another's context. Use when the API accepts a batch array or HTTP/2 multiplexed requests that share processing context

Repository
authzmap ↗
Licence
MIT
Last repository change
28.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Check that batched requests cannot mix identities, credentials or objects so one operation borrows another's context. Use when the API accepts a batch array or HTTP/2 multiplexed requests that share processing context

Original author description

Check that batched requests cannot mix identities, credentials or objects so one operation borrows another's context. Use when the API accepts a batch array or HTTP/2 multiplexed requests that share processing context

How it works

  1. Procedure
  2. Signals
  3. Patterns
  4. Pitfalls
  5. Done when
  6. References
Original SKILL.md headings · 63 lines, 360 words
SKILL.md preview
---
name: batch-request-object-isolation
description: "Check that batched requests cannot mix identities, credentials or objects so one operation borrows another's context. Use when the API accepts a batch array or HTTP/2 multiplexed requests that share processing context"
pack: authzmap
version: 1.0.0
category: api-security
tags: [batch, isolation, object-level]
---

# Batch Request Object Isolation

> Check that batched requests cannot mix identities, credentials or objects so one operation borrows another's context

**Use when:** the API accepts a batch array or HTTP/2 multiplexed requests that share processing context

**Avoid when:** each request is handled strictly independently with no shared context between them

## Procedure

1. Identify how batches are accepted and how context is established: one credential for the batch or one per item.
2. Send a batch where items alternate between your two test accounts' object identifiers under a single credential.
3. Send a batch carrying two different credentials, if supported, and check whether the first item's context leaks into later items.
4. Observe error handling: does one failed item abort the batch, reveal others' results, or alter shared state?
5. Check for ordering effects where an earlier item changes context that later items inherit.
6. Record per-item outcomes so context bleed is attributable to a specific item position.

## Signals

- Items later in the batch return data matching the context of an earlier item rather than their own.
- Per-item credentials are accepted and one item's role applies to subsequent items.
- An error in item one returns partial results from items that should have been refused.
- Batch responses include fields that belong to a different item's object.

## Patterns

**1. Mixed batch**

```text
items: [fetch(peer-id), fetch(my-id)] under my credential
expected: refuse + succeed   observed: both succeed -> finding
```

**2. Context test**

```text
item1 credential=A role=member, item2 credential=B role=admin
-> if item2 returns admin data, context bled from item1
```

**3. Result row**

```text
batch_size=4 mixed=peer-items=2 leaked=0 outcome=refused-cleanly
```

## Pitfalls

- Testing batches that contain only your own objects, which cannot expose context mixing.
- Ignoring partial-success semantics that silently return unauthorized results alongside errors.
- Forgetting write operations in the batch, where context bleed causes cross-account modification.

## Done when

- Mixed-object and mixed-credential batches have been executed with per-item outcomes recorded.
- Context bleed is ruled in or out for read and write items, and ordering effects are documented.

## References

- [OWASP API Security Top 10](https://owasp.org/www-project-api-security/)
- [JSON:API - compound documents](https://jsonapi.org/)

Versions

The database has no other skills named batch-request-object-isolation.

Database snapshot: 13.11.2026 · package version 906e89f96d32 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100batch-write-single-record-scope
    Send a batch containing many entries and one that differs from the rest, because a batch that mutates as a unit can change records you never intended to touch. Use when the API accepts an array or batch of items for a write operation
  • 100batch-envelope-partial-signature
    Examine whether a batch delivery signs every item it carries or only the envelope, since an unsigned item riding inside a signed array is an unauthenticated event. Use when the receiver accepts an array or batch of events under one signature

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.