AI agents use create_spg_nft_collection to create or update resources in Story SDK MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Story SDK MCP Server environment.
Based on the name, this tool likely creates a new SPG (Story Protocol Gateway) NFT collection, which is a Write operation (creating a new on-chain collection). The description is empty, reducing confidence. Given the blockchain/NFT context, creating a collection could have significant financial/resource implications, warranting high severity.
From the tool's definition Tool name: create_spg_nft_collection; description is empty. Sibling tools context includes minting tokens, registering IP, and uploading metadata.
Documented attack patterns abuse exactly the kind of access create_spg_nft_collection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Story SDK MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_spg_nft_collection:
{
"version": "1",
"default": "deny",
"tools": {
"create_spg_nft_collection": {
"limits": [
{
"counter": "create_spg_nft_collection_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_spg_nft_collection stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
create_spg_nft_collection. It is categorised as a Write tool in the Story SDK MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Story SDK MCP Server MCP server in PolicyLayer and add a rule for create_spg_nft_collection: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Story SDK MCP Server. Nothing to install.
create_spg_nft_collection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_spg_nft_collection rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for create_spg_nft_collection. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
create_spg_nft_collection is provided by the Story SDK MCP Server MCP server (piplabs/story-mcp-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Story SDK MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 Story SDK MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.