Create a new Mycelia request. Pass title, body, optional target_agent_id (for directed requests), tags, type, max_responses, expires_hours, priority, and scope tier. Returns the new request ID.
AI agents use mycelia_post_request to create or update resources in Mycelia — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mycelia environment.
An AI agent can call mycelia_post_request faster than any human can review — one bad instruction and it creates or modifies resources in Mycelia by the hundred, each call as confident as the last.
Documented attack patterns abuse exactly the kind of access mycelia_post_request gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mycelia, and nothing reaches the server without passing your rules. This is the rule we recommend for mycelia_post_request:
{
"version": "1",
"default": "deny",
"tools": {
"mycelia_post_request": {
"limits": [
{
"counter": "mycelia_post_request_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mycelia_post_request 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 a new Mycelia request. Pass title, body, optional target_agent_id (for directed requests), tags, type, max_responses, expires_hours, priority, and scope tier. Returns the new request ID. It is categorised as a Write tool in the Mycelia MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mycelia MCP server in PolicyLayer and add a rule for mycelia_post_request: 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 Mycelia. Nothing to install.
mycelia_post_request 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 mycelia_post_request 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 mycelia_post_request. 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.
mycelia_post_request is provided by the Mycelia MCP server (northwoodssentinel/mycelia-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Mycelia tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Mycelia tools catalogued and risk-classified — across an index of 42,500+ MCP servers.