Create a feature request with design documentation
AI agents use create_feature_request to create or update resources in Obsidian Ai Curator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian Ai Curator environment.
This tool creates new data (feature request + documentation) which is reversible through deletion or editing. It has moderate severity because creating feature requests in an issue tracker could generate noise or clutter in workflows, but the effect is not destructive, financial, or code-execution based. Confidence is high because the name and description clearly indicate a creation/write action.
From the tool's definition Tool name 'create_feature_request' indicates creation of new data. Description states 'Create a feature request with design documentation' - a write operation that generates and stores new content in the Obsidian vault or connected issue tracking system.
Documented attack patterns abuse exactly the kind of access create_feature_request gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian Ai Curator, and nothing reaches the server without passing your rules. This is the rule we recommend for create_feature_request:
{
"version": "1",
"default": "deny",
"tools": {
"create_feature_request": {
"limits": [
{
"counter": "create_feature_request_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_feature_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 feature request with design documentation. It is categorised as a Write tool in the Obsidian Ai Curator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian Ai Curator MCP server in PolicyLayer and add a rule for create_feature_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 Obsidian Ai Curator. Nothing to install.
create_feature_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 create_feature_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 create_feature_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.
create_feature_request is provided by the Obsidian Ai Curator MCP server (nwant/obsidian-ai-curator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian Ai Curator, 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.
27 Obsidian Ai Curator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.